chore: prepare SDK 3.0.0 and OTel 2.0.0 release - #1047

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Issue Link, if available

Prepare the coordinated major release from merged #924.

Description

This PR prepares the release sdk-3.0.0 / otel-2.0.0 / test-1.3.2. It adds:

• Release notes with per-package changes, each cited by merge commit. They cover main through 9de0c7f2.
• A 2.x-to-3.0 migration guide.
• A change summary under Unreleased in CHANGELOG.md.
• The release decisions in RELEASING.md.
• Version bumps for three packages that npm already has. This PR changes no runtime code and no publishing workflow.

Package versions

npm state checked on 2026-10-25 with npm view. The publisher decision comes from running decide-dist-tag.js against that state.

Core, OTel and Testing versions come from #924.

Why three packages are bumped

1. The publisher skips a version that npm already has.
2. Telemetry Exporter and MCP 0.1.0-alpha.0 were published on 2026-10-22, outside the release workflow. npm records their gitHead as 6597e075, the refactor(sdk): create one plugin instance per invocation #924 merge commit.
3. So the 3 exporter fixes and 3 MCP fixes merged after 6597e075 need a new version. This PR uses 0.1.0-alpha.1. It does not take the 1.0.0 bump from chore(telemetry): bump exporter and MCP to 1.0.0 #1030.
4. ESLint plugin 1.1.1 was published on 2026-08-14. The new rule from 3cbb456c and e2f013fa needs a new version. This PR uses the minor bump 1.2.0.

0.0.2 was considered for the exporter and rejected. It sorts below 0.1.0-alpha.0. So the publisher would put it on a v0 tag, and latest would keep the version without the fixes.

After publishing

The manual publication left latest on 0.1.0-alpha.0 for both Telemetry packages. The publisher puts 0.1.0-alpha.1 on beta and does not move latest. So a maintainer must run:

npm dist-tag add @aws/durable-execution-sdk-js-telemetry-exporter@0.1.0-alpha.1 latest
npm dist-tag add @aws/durable-execution-sdk-js-telemetry-mcp@0.1.0-alpha.1 latest

The published exporter 0.1.0-alpha.0 requires Core >=3.0.0 <4.0.0. npm cannot satisfy that peer until Core 3 is published.

Not published by this release

Extras and MicroVM Worker stay excluded from automatic publishing. Their changes on main are not in this release. The Telemetry CDK stack is not in the npm package. Its fixes ship from the repository.

Work not included

If any of these merges before the release commit is selected, update the release notes. Refresh the notes against the selected release commit before publishing the GitHub Release.

Demo/Screenshots

Not applicable. The release notes and migration guide are included for review.

Checklist

• I have filled out every section of the PR template
• I have thoroughly tested this change

Testing

Unit Tests

• ESLint plugin: 168 tests passed with version 1.2.0. The plugin reads meta.version from package.json.
• Telemetry MCP: npm run build passed. dist/server.js contains 0.1.0-alpha.1.
• package-lock.json changes only the three version fields.
• Earlier: 102 plugin-loader and invocation-lifetime tests passed for the migration guide.

Integration Tests

The failed integration-tests (24.x) run on 5519e9f0 was parent-context-in-step (cloud). It exceeded its 5 s Jest timeout against the cloud function. That commit changed only Markdown files, and the same job passes on main. This push runs it again.

Earlier: the migration examples typechecked against built Core 3 / OTel 2 declarations, in ESM and CJS, with strict checking and skipLibCheck: false. No package publication or cloud acceptance is claimed.

Examples

• Merged main at 9de0c7f2 without conflicts.
• Ran decide-dist-tag.js against live npm state for 0.0.2, 0.1.0-alpha.1 and 0.1.0.
• Checked each release-note claim against the merge commits and source. Examples: the 3 ms cooldown constant, the faas.max_memory byte conversion, and onOperationEnd running through fireAndForget.
• Relative links resolve. git diff --check passes. No prose semicolons remain.